3 kinds of messaging output:

1) progress events

2) logging (including errors)

3) errors

Progress Events:  1) reading & parsing the input
                  2) generating & merging, for each type
                        < could have this be 1 event per type >
                  3) "updating" (framework does this one)
                  
Logging: mainly errors, plus sources of input, and where output goes. also
includes messages from UIMA code that are directed to the UimaFramework.getLogger()


Errors: Should go to Logger, and in IDE - create markers on resources
or project if no resources to tag to.
  Error Interface: 
    newError(sev, msg)enough to create marker: message & severity

Logger should go to wherever UIMA Logger goes.

Design:  3 interfaces:  
   a IProgressMonitor, 
   UIMA logger,
   IError,   < - maybe not, have "throw" strategy instead?
   
3 use cases:
  Stand-alone (no Eclipse)
    IProgressMonitor routed to UIMA logger
    Log -> UIMA Logger -> System.out
    Errors -> same as log, but throw.
    
  Headless Eclipse
    same
    same
    same
  Eclipse as IDE
    IPRogressMonitor to progressMonitor
    Log -> UIMA logger -> System.out (thrown away?)
    Errors -> markers on resources + listing in task/problem area
  
  